Pcrf triggered rules cleanup

ABSTRACT

Various embodiments relate to a system and related method of handling a plurality of user messages originating from a user device in a communications network. Various embodiments relate to a Policy Charging and Rules Node (PCRN) receiving an initial message from a first device, while anticipating a complementary message from a second device. Upon receipt of the complementary message, the PCRN may pair the messages and generate a rule from the paired message. If the PCRN does not receive the complementary message, the PCRN may generate the rule from only the initially-received message or may ignore the message. The PCRN may treat each received message independent from each other so that lack of receipt of a complementary message does not affect the creation of rules from another paired message.

TECHNICAL FIELD

Various exemplary embodiments disclosed herein relate generally topolicy and charging in telecommunications networks.

BACKGROUND

As the demand increases for varying types of applications within mobiletelecommunications networks, service providers must constantly upgradetheir systems in order to reliably provide this expanded functionality.What was once a system designed solely for voice communications hasrecently grown into a heterogeneous system that enables access tocommunications platforms such as text messaging, multimedia streamingalong with general Internet access. To support such applications,service and infrastructure providers have built new networks overexisting voice communication infrastructure. As evidenced by second andthird generation networks, voice services must be carried over dedicatedvoice channels toward a traditional circuit-switched core, while otherservices, such as IP-enabled data and communications may be transmittedover a different packet-switched core, following Internet protocol (IP).This has led to unique problems, including, for example, applicationprovision, metering and charging, and quality of experience (QoE)assurance.

One recent attempt to enhance the dual-core approach of the second (2G,2.5G) and third generations (3G) of mobile telecommunications standardsdefined by the International Telecommunications Union has been in theform of a new set of standards. The Third Generation Partnership Project(3GPP) has recommended a new network scheme deemed ‘Long Term Evolution’(LTE). Under the new standards, all communications in an LTE network arecarried over an IP channel from user equipment (UE), such as a mobilephone or smartphone, to an all-IP core named the Evolved Packet Core(EPC). The EPC may then provide gateway access to other networks, whilealso ensuring an acceptable QoE for a user's network activity andproperly charging the subscriber for such activity.

The 3GPP generally describes the components of the EPC and theirinteractions with each other in some technical specifications,specifically, 3GPP TS 29.212, 3GPP TS 29.213, and 3GPP TS 29.214, whichdescribe components such as a Policy and Charging Rules Function (PCRF),Policy and Charging Enforcement Function (PCEF), and Bearer Binding andEvent Reporting Function (BBERF) of the EPC. These technicalspecifications also provided some details regarding the interactionsbetween these components. These specifications gave some guidance on howthe EPC could provide reliable data services to users, while alsoreliably charging subscribers for use of the IP network.

For example, 3GPP TS 29.212, 3GPP TS 29.213, and 3GPP TS 29.214 providesome guidance on rule generation by the PCRF when receiving messagesfrom at least two different sources, such as, for example, theapplication function (AF) and the PCEF. These specifications providesome guidance, for example, for when the PCRN receives the first of atwo-part message. However, the algorithm outlined by the specificationsmay not always work efficiently under certain circumstances.

In view of the foregoing, it would be desirable to provide a system andmethod more capable of handling complementary messages. In particular,it would be desirable to provide a system that may handle complementarymessages for a range of circumstances.

SUMMARY

In light of the present need for a method for handling the anticipatedreceipt of paired messages, a brief summary of various exemplaryembodiments is presented. Some simplifications and omissions may be madein the following summary, which is intended to highlight and introducesome aspects of the various exemplary embodiments, but not to limit thescope of the invention. Detailed descriptions of a preferred exemplaryembodiment adequate to allow those of ordinary skill in the art to makeand use the inventive concepts will follow in the later sections.

Various embodiments may relate to a method performed by a PolicyCharging and Rules Node (PCRN) to handle a plurality of requests from auser device for service in a communications network. The method mayinclude the PCRN receiving, from a first gateway, a plurality of initialrequests to establish a plurality of services for the user device. ThePCRN may then create a rule for each of the received initial requests insaid plurality of initial requests and wait for a defined period toreceive at least one complementary request from a second gateway,wherein each complementary request matches one of the received initialrequests in the plurality of initial requests. The PCRN may then receivefrom the second gateway at least one complementary request, form atleast one paired request after the defined period by matching each ofthe at least one received complementary request with one of theplurality of received initial requests, and remove each rulecorresponding to each received request that is not part of the at leastone paired request.

Various embodiments may also relate to a system for handling a pluralityof requests from a user device for service in a communications network.The system may include the user device that requests a plurality ofservices. The system may also include a first gateway that transmits aplurality of initial requests to establish the plurality of services forthe user device and a second gateway that transmits at least onecomplementary request to establish at least one service from theplurality of services for the user device, wherein the at least onecomplementary request matches at least one initial request from theplurality of requests. The system may also include a Policy and ChargingRules Node (PORN) that receives the plurality of initial requests andthe at least one complementary request. The PORN in the system maycreate a rule for each of the plurality of initial requests received,wait for a defined period to receive the complementary requests, form atleast one paired request after the defined period by matching each ofthe at least one complementary request with one of the plurality ofreceived initial requests, and remove each rule corresponding to eachreceived request that is not part of the at least one paired request.

It should be apparent that, in this manner, various exemplaryembodiments enable dynamic handling of complementary messages frommultiple sources. Particularly, by enabling the PCRN to control thehandling of complementary messages, the PCRN may more efficientlyprocess requests from a user device.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to better understand various exemplary embodiments, referenceis made to the accompanying drawings wherein:

FIG. 1 illustrates an exemplary subscriber network for providing variousdata services;

FIG. 2 illustrates an exemplary network for a policy charging and rulesnode (PCRN) receiving complementary service requests; and

FIG. 3 illustrates an exemplary flowchart for generating a rule whenreceiving a message from an application node.

DETAILED DESCRIPTION

Referring now to the drawings, in which like numerals refer to likecomponents or steps, there are disclosed broad aspects of variousexemplary embodiments.

FIG. 1 illustrates an exemplary subscriber network 100 for providingvarious data services. Exemplary subscriber network 100 may be atelecommunications network or other network for providing access tovarious services. Exemplary subscriber network 100 may include at leastone piece of user equipment (UE) 110, a base station 120, an evolvedpacket core (EPC) 130, a packet data network 140, and an applicationnode (AN) 150.

User equipment (UE) 110 may be a device that communicates with thepacket data network 140 for providing the end-user with a data service.Such data service may include, for example, voice communication, textmessaging, multimedia streaming, and Internet access. Specifically, invarious exemplary embodiments, UE 110 is a personal or laptop computer,wireless e-mail device, cellular phone, television set-top box, or anyother device capable of communicating with other devices via the EPC130.

Base station 120 may be a device that enables communication between UE110 and the EPC 130. For example, the base station 120 may be a basetransceiver station such as an evolved nodeB (eNodeB) as defined by 3GPPstandards. Thus, the base station 120 may be a device that communicateswith the UE 110 via a first medium, such as radio communication, andcommunicates with the EPC 130 via a second medium, such as an Ethernetcable. Base station 120 may be in direct communication with the EPC 130or may communicate via a number of intermediate nodes (not shown in FIG.1). In various embodiments, multiple base stations (not shown) similarto the base station 120 may be present to provide mobility to the UE110. In various alternative embodiments, UE 110 may communicate directlywith the EPC 130. In such embodiments, the base station 120 may not bepresent.

Evolved packet core (EPC) 130 may be a device or network of devices thatprovides the UE 110 with gateway access to the packet data network 140.EPC 130 may further charge a subscriber for use of provided dataservices and ensure that particular quality of experience (QoE)standards are met. Thus, the EPC 130 may be implemented, at least inpart, according to the 3GPP TS 29.212, 29.213, 29.214 technicalspecifications. Accordingly, the EPC 130 may include a serving gateway(SGW) 132, a packet data network gateway (PGW) 134, a policy andcharging rules node (PCRN) 136, and a subscription profile repository(SPR) 138.

Serving gateway (SGW) 132 may be a device that provides gateway accessto the EPC 130. SGW 132 may be the first device within the EPC 130 thatreceives packets sent by the UE 110. SGW 132 may forward such packetstowards the PGW 134. SGW 132 may perform a number of functions such as,for example, managing mobility of user equipment 110 between multiplebase stations (not shown) and enforcing particular quality of service(QoS) characteristics, such as guaranteed bit rate, for each flow beingserved. In various implementations, such as those implementing the ProxyMobile Internet Protocol (PMIP) standard, the SGW 132 may include aBearer Binding and Event Reporting Function (BBERF). In variousexemplary embodiments, the EPC 140 may include multiple SGWs (not shown)similar to the SGW 132 and each SGW may communicate with multiple basestations (not shown) similar to the base station 120.

Packet data network gateway (PGW) 134 may be a device that providesgateway access to the packet data network 140. PGW 134 may be the finaldevice within the EPC 130 that receives packets sent by user equipment110 toward the packet data network 140 via the SGW 132. PGW 134 mayinclude a policy and charging enforcement function (PCEF) that enforcespolicy and charging control (PCC) rules for each service data flow(SDF). Thus, the PGW 134 may be a policy and charging enforcement node(PCEN). PGW 134 may include a number of additional features, such as,for example, packet filtering, deep packet inspection, and subscribercharging support.

Policy and charging rules node (PCRN) 136 may be a device that receivesrequests for services, generates PCC rules, and provides PCC rules tothe PGW 134 and/or other PCENs (not shown). PCRN 136 may be incommunication with AN 150 via an Rx interface. PCRN 136 may receiverequests from AN 150, SGW 132, or PGW 134. Upon receipt of a servicerequest, PCRN 136 may generate at least one new PCC rule for fulfillingthe service request.

PCRN 136 may also be in communication with SGW 132 and PGW 134 via a Gxxand a Gx interface, respectively. Upon creating a new PCC rule or uponrequest by the PGW 134, PCRN 136 may provide a PCC rule to PGW 134 viathe Gx interface. In various embodiments, such as those implementing thePMIP standard for example, PCRN 136 may also generate QoS rules. Uponcreating a new QoS rule or upon request by the SGW 132, PCRN 136 mayprovide a QoS rule to SGW 132 via the Gxx interface.

PCRN 136 may receive related requests from a plurality of sources andmay generate a FCC rule for fulfilling the service request related tothe related requests. For example, a UE 110 may transmit a request forservice. PCRN 136 may receive a first request from the AN 150 and asecond, related request for service from the PGW 134. PCRN 136 may pairthe related requests together and generate a rule, e.g., a PCC rule, andsend the generated rule to both the AN 150 and the PGW 134

Subscription profile repository (SPR) 138 may be a device that storesinformation related to subscribers to the subscriber network 100. Thus,SPR 138 may include a machine-readable storage medium such as aread-only memory (ROM), a random-access memory (RAM), magnetic diskstorage media, optical storage media, flash-memory devices, and/orsimilar storage media. SPR 138 may be a component of PCRN 136 or mayconstitute an independent node within EPC 130. Data stored by SPR 138may include an identifier of each subscriber and indications ofsubscription information for each subscriber such as bandwidth limits,charging parameters, and subscriber priority.

Packet data network 140 may be any network for providing datacommunications between user equipment 110 and other devices connected topacket data network 140, such as AN 150. Packet data network 140 mayfurther provide, for example, phone and/or Internet service to varioususer devices in communication with packet data network 140.

Application node (AN) 150 may be a device that includes an applicationfunction (AF) and provides an application service to user equipment 110.Thus, AN 150 may be a server or other device that provides, for example,a video streaming or a voice communication service to user equipment110. AN 150 may further be in communication with the PCRN 136 of the EPC130 via an Rx interface. When AN 150 is to begin providing applicationservice to user equipment 110, AN 150 may generate a request message,such as an AA-Request (AAR) according to the Diameter protocol, tonotify the PCRN 136. This request message may include information suchas an identification of the subscriber using the application service andan identification of the particular service data flows that must beestablished in order to provide the requested service. AN 150 maycommunicate such an application request to the PCRN 136 via the Rxinterface.

FIG. 2 illustrates an exemplary communications network, with a PCRNreceiving multiple messages for a service request. System 200 is similarto system 100, with application node (AN) 201, policy and charging rulesnode (PCRN) 202, packet data network gateway (PGW) 203, user equipment204, and packet data network 205 corresponding to AN 150, PCRN 136, PGW134, UE 110, and packet data network 140, respectively.

In system 200, UE 204 may send multiple related service requests throughmultiple devices, such as AN 201 and PGW 203, with the requesteventually being sent to PCRN 202. PCRN 202 may then take the receivedservice requests and form a plurality of services, using with thereceived information and other available information stored at the PCRN202. PCRN 202 may then implement the service and may also formassociated rules, forwarding the created rules to PGW 203, which maythen transmit the rules to other gateways, such as SGW 132.

UE 204 may, for example, send a session initiation protocol (SIP)service request that may be handled by application node (AN) 201. AN 201may receive the service request through packet data network 205 and PGW203. AN 201 may package the received service request into a message(MSG1) that may then be sent to the PCRN 202 via the Rx interface. Themessage sent by AN 201 may include information regarding connectiondetails, such as the required bandwidth and type of media (e.g., voice,video, data, etc.) required. In some embodiments, the message sent bythe AN 201 to the PCRN 202 may take precedent over messages the PCRN 202receives from other components, so that when PCRN 202 receivesconflicting messages from other components (e.g., PGW 203), the PCRN 202uses the information included in the message received from AN 201.

The message sent by the AN 201 may be in the form of an AA-Requestcommand. The AA-Request command may include a plurality of information,including the IP address of the UE 204 (for example, in aForward-IP-Address attribute-value pair (AVP) or Framed-IPv6-Prefix AVP)and other service information (e.g., in a Media-Component-DescriptionAVP). The AA-Request may also include information indicating theparticular service to which a session may belong (for example, in anAF-Application-Identifier AVP).

UE 204 may also send another service request related to the SIP servicerequest previously through the AN 201. The related service request(e.g., complementary request) may be paired with the initial servicerequest sent through the AN 201. The complementary service request maybe sent through the PGW 203 to the PCRN 202, where the PGW 203 sends thecomplementary service request in the form of a CC Request message. PGW203 may therefore send a message in that includes a CC Request. The CCRequest may include an Event-Trigger AVP and a Packet-Filter-OperationAVP, which may trigger certain actions by the PCRN 202, which will bediscussed below in relation to FIG. 3. The CC Request may also include acorresponding Packet-Filter-Information AVP.

PGW 203 may include a policy charging and enforcement function (PCEF),which may include the complementary service request in a message (MSG2)that is sent to the PCRN 202. The message sent from the PGW 203 may bethe mate message to the message (MSG1) sent from the AN 201, as the PCRN202 may use information from both received messages (e.g., pairedmessage) when creating a PCC rule. The information included in themessage sent from PGW 203 may include other communication requirements,such as the required guaranteed bit rate. The information included inthe message sent through the PGW 203 may be related to the requirementsfor the UE 204 to connect to the packet data network.

The PCRN 202 may receive one or messages containing information and mayuse the information to form at least one PCC rule. PCRN 202 may usedifferent procedures to produce a rule based on the initial message itreceives. For example, if the PGW 203 containing the PCEF solicits arequest for the provisioning of the PCC rule, the PCRN 202 may implementa PUSH procedure, as will be discussed further in relation to FIG. 3,wherein the PCRN 202 provisions the PCC rule in a Re-authorizationRequest (RAR) command to the PGW 203. Alternatively, when the request isunsolicited (e.g., the first request comes from AN 201), the PCRN 202may implement a PULL command, wherein PCRN 202 creates a PCC rule andincludes the PCC rule in a CCA message.

The UE 204 may send one or more service requests simultaneously to thePCRN 202. In some embodiments, the plurality of service requests may befor related services. In other embodiments, the UE 204 may request oneor more unrelated services from the PCRN 202. In some embodiments, thePCRN 202 may handle the plurality of service requests as completelyunrelated and may handle the requests independent of each other. Inother embodiments, the PCRN 202 may handle the plurality of servicerequests as related and may either enable or deny service based on thehandling of each request in the plurality.

Having described the components of subscriber network 100, 200 a briefsummary of the operation of subscriber network 100, 200 will beprovided. It should be apparent that the following description isintended to provide an overview of the operation of subscriber network100, 200 and is therefore a simplification in some respects. Thedetailed operation of subscriber network 100, 200 will be described infurther detail below in connection with FIG. 3.

According to various exemplary embodiments, user equipment (UE) 204 maycommunicate with a plurality of devices, including the AN 201, SGW 132,or PGW 203 to indicate that user equipment 204 wishes to receiveservice. Such communication may occur via EPC 130 and packet datanetwork 205 or via other communications channels (not shown). AN 201,SGW 132, or PGW 203 may then construct a message, including some of thenecessary subscriber and data flow information necessary to provide therequested service. All of the necessary information may be scatteredacross multiple devices, such as the AN 201, SGW 132, SPR 138, and thePGW 203. AN 201, SGW 132, SPR 138 or PGW 203 may then forward thegenerated message to the PCRN 202 through the requisite interface.

Upon receipt of a first plurality of initial messages 221-225, the PCRN202 may wait for an equal quantity of complementary messages. In someembodiments, the PCRN 202 may wait for a defined period by starting atimer upon receipt of the first plurality of messages. In someembodiments, the PCRN's 202 initiation of the timer may move thecreation of the rule to the end of an execution queue for the PCRN 202.For example, PGW 203 may send a first plurality of initial messages221-225 to the PCRN 202, which may then anticipate receiving a secondplurality of complementary messages 231-233 for each of the receivedinitial messages 221-225. The PCRN 202 may then place the generation ofthe PCC rule to the end of its execution queue, effectively waiting forthe second plurality of complementary messages to arrive while executingother functions. When the PCRN 202 receives the second plurality ofcomplementary messages 231-233 before the timer expires and the quantityof complementary messages is equal to the quantity of received initialmessages, the PCRN 202 may immediately generate a quantity of rulesequal to the plurality of initial messages 221-225. PCRN 202 may useinformation from each set of paired messages (i.e., an initial message221 and a complementary message 231) to create each rule.

However, when the second plurality of complementary messages 231-233does not completely arrive before the timer expires, the PCRN 202 maythen generate a quantity of rules from the plurality of complete pairedmessages, i.e., initial messages 221-223 and complementary messages231-233. In some embodiments, the PCRN 202 may take no further actionsfor those received initial rules 225 for which the PCRN 202 did not alsoreceive a complementary message. In some embodiments, the PCRN 202 mayattempt to generate a rule using available information from at least thereceived initial message 225. The PCRN 202 may also attempt to includeinformation from existing rules. PCRN 202 may also take subscriber datafrom SPR 138 and internally-generated policy decisions into account whendetermining whether to attempt generating a rule from only the initialmessage 225.

PCRN 202 may then transmit the generated PCC rule to PGW 203 via the Gxinterface for installation. In some embodiments, the PCRN 202 mayreceive the missing complementary message (not shown) after the definedperiod. PCRN 202 may thereafter generate a new rule using both theinitial message 225 and complementary message. The new rule may replacethe previously-crafted rule that only used information from the initialmessage 225. After installation of either the first or second rule, thePCRN 202, through devices such as SGW 132 and PGW 203, may thereforeallow communication for the requested service, while also enablingfurther functionality by, for example, enabling the appropriate chargingof the subscriber and ensuring that a particular QoS is met.

FIG. 3 illustrates an exemplary flowchart for creating a new rule inresponse to a service request from the UE 204. PCRN 202 may implementmethod 300 when it receives, for example, a service request from the UE204 through the AN 201 and/or PGW 203.

Method 300 may begin at step 301 and proceed to step 303, where the PCRN202 may receive a message from the UE 204. In some embodiments, the PCRN202 may receive a service request from AN 201 in the form of a serviceflow via the Rx interface. Because the PCRN 202 receives a message fromthe AN 201 first, the corresponding PCC rule may be labeled as“Network-Initiated.” The service flow may be derived from a hierarchy ofcomponents in an AN message. An AN message may consist of a plurality ofMedia Components (MC), with each Media Component containing a pluralityof Media Sub-Components (MSC). Each Media Sub-Component may containeither one or two flow descriptions (FD). The service flow may be aflattened representation of this hierarchy, matching the one or two flowdescriptions with the corresponding MCs and MSCs. Each service flow maymap to a distinct rule that may be installed in the gateways SGW 132 orPGW 134. Accordingly, the rule may contain a reference to the serviceflow used in its creation.

In another embodiment, the PCRN 202 may first receive a service requestfrom PGW 134 that includes flow information. The flow information may becontained within a Packet-Filter-Information AVP included in the servicerequest. The service request may also include a correspondingPacket-Filter-Operation AVP. In this instance, because the PGW 134initiated the service request, the corresponding rule may be labeled as“UE-Initiated.” In some embodiments, the CC Request that comprised theservice request may include a Packet-Filter-Information AVP for eachpacket filter requested by the UE 204 and a QoS-Information AVP that mayindicate the requested quality of service for the packet filter.

Method 300 may then proceed to step 305, where the PCRN 202 maydetermine whether it is storing a message that is a companion to thereceived message. In some embodiments, this may be an initially-receivedmessage or a created rule that matches the received service flow. Inother embodiments, the companion message may be an initially-receivedservice flow that matches the received flow information.

If there is a companion rule stored in the PCRN 202, method 300 mayproceed to step 307, where the PCRN 202 may pair the received messagewith the stored companion message. PCRN 202 may create a paired messagewhen combining the initially-received, stored companion message with themessage received. In step 309, the PCRN 202 may create a rule usinginformation contained in the paired message. The information containedin the paired message may include all the information contained in boththe initially received, the stored message, and the subsequentlyreceived message. In step 311, the PCRN 202 may forward the new rule tothe PCEF in PGW 134, which may in turn push the new rule to othergateways. PCRN 202 may then end method 300 at step 313.

If there is no companion message, this may indicate that the receivedmessage initiated the request for a rule, so the method proceeds to step321, where the PCRN 202 may wait for a defined period. PCRN 202 maystart a timer to wait to receive the mate message. PCRN 202 may wait forthe mate message because the mate message may contain informationcomplementary to the initially-received message. For example, if thePCRN 202 initially received a message from AN 201 in step 303, in step321, the PCRN 202 may wait for a defined period to receive acomplementary message from PGW 134.

PCRN 202 may wait until either the timer expires or the complementarymessage arrives. In either case, method 300 proceeds to step 323-325,where the PCRN 202 determines if it received a message during thewaiting period and if the newly-received message is complementary to theinitially-received message. If the PCRN 202 did receive a complementarymessage, method 300 may then proceed to steps 307-311, where the PCRN202 binds the two messages into a paired message, creates a rule fromthe paired message, and pushes the newly-created rule to the gateways.

PCRN 202 may then proceed to step 327, where it may determine whetherthe subscriber of the UE 204 has access to unknown services. In someembodiments, the PCRN 202 may determine whether the subscriber hasaccess to unknown services through contact with the SPR 138. If thesubscriber does not have access to unknown services, method 300 may thenproceed to step 329. In this instance, the PCRN 202 may modify notgenerate a rule with the available information, which may only includethe initially-received message. PCRN 202 may then end method 300 at step313.

Returning now to step 327, if the PCRN 202 determines that thesubscriber has access to unknown services, the PCRN 202 may generaterule using the information included in the PCRN 202. In someembodiments, the PCRN 202 may generate a rule with only the informationincluded in the initially-received message. In other embodiments, thePCRN 202 may use information from other stored services, such asinformation included in an associated unknown application. In someembodiments, the subscriber access to unknown services may be specificto the service. For example, the SPR 138 may hold records that state asubscriber has access to unknown voice services, but does not haveaccess to unknown data services. After generating a new rule usingavailable information, the PCRN 202 may proceed to step 333, where itpushes the newly-generated rule to the PCEF in PGW 134, which may thenpush the new rule to the other gateways. PCRN 202 may then end method300 in step 313.

During regular operation, the PCRN 202 may enact method 300 for eachmessage received. In some embodiments, the PCRN 202 may thereforeindependently create rules for paired messages, while ignoring expectedpaired messages when the PCRN 202 receives only a portion of the pair.For example, if the PCRN 202 receives initial messages 221-225, the PCRN202 may wait to receive complementary messages 231-235. Whencomplementary messages 231-233 arrive, the PCRN 202 may enact method 300for each received message to pair the subsequently-received messages231-233 with initially-received messages 221-223. As the PCRN 202 didnot receive complementary message 235 (not shown), the PCRN 202 may notgenerate a rule for that message if the subscriber does not have accessto unknown services.

Therefore, the PCRN 202 may handle the creation of rules independently,instead of, for example, dropping an entire bundle of messages if it didnot receive complementary messages for each member of the bundle. Thismay save time and bandwidth, for example, as the PCRN 202 may onlyrequire the UE 204 to resend the missing pair of messages instead of theentire bundle. In some embodiments, the PCRN 202 may also save time andbandwidth by enabling the creation of a rule when a subscriber hasaccess to unknown services and the PCRN 202 only receives a portion ofan expected paired message.

According to the foregoing, various exemplary embodiments provide fordynamic creation of rules in response to the expected receipt of pairedmessages from multiple devices. Particularly, by independentlygenerating rules upon receipt of initial and complementary messages andignoring partially-received paired messages, the PCRN may enable properfunctioning of the communications system, while also boosting efficiencyand minimizing bandwidth.

It should be apparent from the foregoing description that variousexemplary embodiments of the invention may be implemented in hardwareand/or firmware. Furthermore, various exemplary embodiments may beimplemented as instructions stored on a machine-readable storage medium,which may be read and executed by at least one processor to perform theoperations described in detail herein. A machine-readable storage mediummay include any mechanism for storing information in a form readable bya machine, such as a personal or laptop computer, a server, or anothercomputing device. Thus, a machine-readable storage medium may include aread-only memory (ROM), a random-access memory (RAM), magnetic diskstorage media, optical storage media, flash-memory devices, and similarstorage media.

It should be appreciated by those skilled in the art that any blockdiagrams herein represent conceptual views of illustrative circuitryembodying the principals of the invention. Similarly, it will beappreciated that any flow charts, flow diagrams, state transitiondiagrams, pseudo code, and the like represent various processes whichmay be substantially represented in machine readable media and soexecuted by a computer or processor, whether or not such computer orprocessor is explicitly shown.

Although the various exemplary embodiments have been described in detailwith particular reference to certain exemplary aspects thereof, itshould be understood that the invention is capable of other embodimentsand its details are capable of modifications in various obviousrespects. As is readily apparent to those skilled in the art, variationsand modifications can be affected while remaining within the spirit andscope of the invention. Accordingly, the foregoing disclosure,description, and figures are for illustrative purposes only and do notin any way limit the invention, which is defined only by the claims.

1. A method performed by a Policy Charging and Rules Node (PCRN) tohandle a plurality of requests from a user device for service in acommunications network, the method comprising: receiving, from a firstgateway, a plurality of initial requests to establish a plurality ofservices for the user device; creating a rule for each of the receivedinitial requests in said plurality of initial requests; waiting for adefined period to receive at least one complementary request from asecond gateway, wherein each complementary request matches one of thereceived initial requests in the plurality of initial requests;receiving, from the second gateway, at least one complementary request;forming at least one paired request after the defined period by matchingeach of the at least one received complementary request with one of theplurality of received initial requests; and removing each rulecorresponding to each received request that is not part of the at leastone paired request.
 2. The method of claim 1, wherein the plurality ofreceived initial requests is greater in quantity than the plurality ofcomplementary requests.
 3. The method of claim 1, further comprising:signaling, upon the creation of the plurality of rules for each of thereceived initial requests, the first gateway to establish services foreach of the plurality of received initial requests.
 4. The method ofclaim 3, further comprising: removing each service established in thefirst gateway corresponding to each received request that is not part ofthe at least one paired request.
 5. The method of claim 1, furthercomprising: signaling the first and second gateways to establishservices for the at least one paired request.
 6. The method of claim 1,wherein the first and second gateways sending user requests comprise adevice from a list of: a serving gateway, a Packet Data Network Gateway(PGW), and an Application Node (AN).
 7. The method of claim 1, furthercomprising: determining whether a subscriber for the user device onlyhas access to known services; abstaining from removing each rulecorresponding to each received request that is not part of the at leastone paired request when the subscriber has access to unknown services;and removing each rule corresponding to each received request that isnot part of the at least one paired request when the subscriber only hasaccess to known services.
 8. The method of claim 7, wherein the firstgateway: receives a plurality of user requests from the user device;generates the plurality of initial requests corresponding to theplurality of user requests, wherein the at least two initial requestscomprise messages containing a session establishment request andidentification information; and transmits the at least two initialrequests to the PCRN.
 9. The method of claim 8, wherein theidentification information comprises a Session Binding Identifier (SBI)comprising a set of attributes, the attributes including at least oneof: a session identification; an IPv4 address; an IPv6 address; anAccess Point Name (APN); and at least one subscriber identifier (SID);wherein the attributes comprising the SBI also comprise attributes in atleast one subscriber profile corresponding to the subscriber.
 10. Themethod of claim 7, wherein the second gateway: receives a plurality ofuser requests from the user device; generates the plurality of initialrequests corresponding to the plurality of user requests, wherein the atleast two initial requests comprise messages containing a sessionestablishment request and identification information; and transmits theat least two initial requests to the PCRN.
 11. The method of claim 8,wherein the identification comprises a Session Binding Identifier (SBI)comprising a set of attributes, the attributes including at least oneof: a session identification; an IPv4 address; an IPv6 address; anAccess Point Name (APN); and at least one subscriber identifier (SID);wherein the attributes comprising the SBI also comprise attributes in atleast one subscriber profile corresponding to the subscriber.
 12. Asystem for handling a plurality of requests from a user device forservice in a communications network, the system comprising: a firstgateway that, in response to a request for plurality of services by theuser device, transmits a plurality of initial requests to establish theplurality of services for the user device; a second gateway thattransmits at least one complementary request to establish at least oneservice from the plurality of services for the user device, wherein theat least one complementary request matches at least one initial requestfrom the plurality of requests; and a Policy and Charging Rules Node(PCRN) that receives the plurality of initial requests and the at leastone complementary request, wherein the PCRN: creates a rule for each ofthe plurality of initial requests received, waits for a defined periodto receive the complementary requests, forms at least one paired requestafter the defined period by matching each of the at least onecomplementary request with one of the plurality of received initialrequests; and removes each rule corresponding to each received requestthat is not part of the at least one paired request.
 13. The system ofclaim 12, wherein the plurality of received initial requests is greaterin quantity than the plurality of complementary requests.
 14. The systemof claim 12, wherein the PCRN signals, upon the creation of theplurality of rules for each of the received initial requests, the firstgateway to establish services for each of the plurality of receivedinitial requests.
 15. The system of claim 14, wherein the first gatewayremoves each service established corresponding to each received requestthat is not part of the at least one paired request.
 16. The system ofclaim 12, wherein the PCRN signals the first and second gateways toestablish services the at least one paired request.
 17. The system ofclaim 12, wherein the first and second gateways sending user requestscomprise a device from a list of: a serving gateway, a Packet DataNetwork Gateway (PGW), and an Application Node (AN).
 18. The system ofclaim 12, wherein the PCRN further: determines whether a subscriber forthe user device only has access to known services; and removes each rulecorresponding to each received request that is not part of the at leastone paired request when the subscriber only has access to knownservices.
 19. The system of claim 18, wherein the first gateway further:receives a plurality of user requests from the user device; generatesthe plurality of initial requests corresponding to the plurality of userrequests, wherein the at least two initial requests comprise messagescontaining a session establishment request and identificationinformation; and transmits the at least two initial requests to thePCRN.
 20. The system of claim 19, wherein the identification informationcomprises a Session Binding Identifier (SBI) comprising a set ofattributes, the attributes including at least one of: a sessionidentification; an IPv4 address; an IPv6 address; an Access Point Name(APN); and at least one subscriber identifier (SID); wherein theattributes comprising the SBI also comprise attributes in at least onesubscriber profile corresponding to the subscriber.
 21. The system ofclaim 18, wherein the second gateway further: receives a plurality ofuser requests from the user device; generates the plurality of initialrequests corresponding to the plurality of user requests, wherein the atleast two initial requests comprise messages containing a sessionestablishment request and identification information; and transmits theat least two initial requests to the PCRN.
 22. The system of claim 21,wherein the identification information comprises a Session BindingIdentifier (SBI) comprising a set of attributes, the attributesincluding at least one of: a session identification; an IPv4 address; anIPv6 address; an Access Point Name (APN); and at least one subscriberidentifier (SID); wherein the attributes comprising the SBI alsocomprise attributes in at least one subscriber profile corresponding tothe subscriber.